Draft
Conversation
|
Hi, I see you are still busy on this, just wanted to let you know this change is still very much desired from at least me :) |
|
I'm bumping up against this too. Not having proper unit tests working makes me very uncomfortable, haha. I'm on linux and would be happy to test it, but I don't know how to install a quasar app extension from a branch package (it doesn't appear to work the same as pnpm) |
n05la3
added a commit
to n05la3/quasar-testing
that referenced
this pull request
May 7, 2026
- Update Cypress AE for Cypress 15.14+ / Vite 8 / app-vite 2.5+ - Add enforcedCypress15Vite8Compatibility() blocking app-vite 2.4.x (Vite 7) - Bump vite-plugin-istanbul ^7 -> ^8 (Vite 8 compat) - Add v6.2 -> v6.3 migration guide in README - Add ESLint overlay troubleshooting note for stale eslint-disable directives - Remove stale eslint-disable from VModelComponent.cy.ts template - Add moduleResolution: node override in tsconfig.json - Update test-vite-app-v2 to app-vite ^2.5.0 + cypress ^15.14.0 Note: test-vite-app-v2 has 13 component test failures caused by a vite-plugin-checker vue-tsc overlay. The old vitest AE v1 (JS-based) lacks type declarations, causing vue-tsc to render an error overlay that covers interactive elements during Cypress component tests. This will be resolved when PR quasarframework#409 (vitest AE v2, TS rewrite) merges. Also note: test-vite-app-v2-vite8 and test-webpack-app-v4-cypress15 pass all tests clean (no vitest AE installed).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce? (check at least one)
If you are adding a new test runner, have you...? (check all)
/packages/base/runners.json?/README.md?baseline.spec.vue?Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
devbranch and not themasterbranchfix: #xxx[,#xxx], where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information: